Skip to content

feat: Remove OpenRouter support, replace litellm with Chutes API #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
echobt wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: Remove OpenRouter support, replace litellm with Chutes API #9

echobt wants to merge 1 commit into from

Conversation

@echobt
Copy link
Contributor

@echobt echobt commented Feb 3, 2026

Summary

This PR removes OpenRouter support and replaces litellm with direct Chutes API client using httpx.

Changes

  • Remove OPENROUTER from Provider enum, add CHUTES
  • Update get_api_key() to use CHUTES_API_KEY
  • Update get_base_url() to use https://api.chutes.ai/v1
  • Rewrite LLM client using httpx instead of litellm
  • Update default model to deepseek/deepseek-chat
  • Remove litellm from requirements.txt and pyproject.toml
  • Update all documentation references
  • Keep LiteLLMClient alias for backward compatibility

Breaking Changes

⚠️ litellm dependency removed - Projects relying on litellm features need to migrate.
⚠️ OpenRouter no longer supported - Use Chutes API instead.

Migration

# Before
export OPENROUTER_API_KEY="sk-or-..."

# After
export CHUTES_API_KEY="cpk_..."

Testing

python3 -c "from src.llm.client import LLMClient; print('OK')"

Related

@echobt
feat: Remove OpenRouter support, replace litellm with Chutes API
1401763 
- Remove OPENROUTER from Provider enum, add CHUTES
- Update get_api_key() to use CHUTES_API_KEY
- Update get_base_url() to use https://api.chutes.ai/v1
- Rewrite LLM client using httpx instead of litellm
- Update default model to deepseek/deepseek-chat
- Remove litellm from requirements.txt and pyproject.toml
- Update all documentation references
- Keep LiteLLMClient alias for backward compatibility
@coderabbitai
Copy link

coderabbitai bot commented Feb 3, 2026

Warning

Rate limit exceeded

@echobt has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 29 minutes and 33 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/remove-openrouter-litellm

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

This was referenced Feb 3, 2026
Open
Open
@echobt
Copy link
Contributor Author

echobt commented Feb 3, 2026

Part of Umbrella PR: #6 (Epic: Complete Chutes API Integration)

This PR is the final step in the stacked PR sequence:

  1. feat: Integrate Chutes API with Kimi K2.5-TEE model #7 - Chutes API integration (merge first)
  2. docs: Comprehensive documentation with Mermaid diagrams #8 - Documentation (depends on feat: Integrate Chutes API with Kimi K2.5-TEE model #7)
  3. This PR (feat: Remove OpenRouter support, replace litellm with Chutes API #9) - OpenRouter removal (depends on feat: Integrate Chutes API with Kimi K2.5-TEE model #7 and docs: Comprehensive documentation with Mermaid diagrams #8)

Note: After #7 and #8 are merged, this PR should be rebased on main before merging.

Please see #6 for the complete merge strategy.

@echobt echobt mentioned this pull request Feb 3, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@echobt